System And Method For Implicit Authentication

ABSTRACT

A system for implicit authentication for a mobile device associated with a user, wherein the implicit authentication is behavioural, biometric and task-based and includes at least one authentication task selected so as to leverage the user&#39;s muscle memory. The mobile device comprises a touchscreen; a transaction authentication information unit; one or more sensors coupled to the transaction authentication information unit; and an anomaly detector coupled to the transaction authentication information unit. The sensors comprise one or more touchscreen sensors coupled to the touchscreen, an accelerometer, and a gyroscope, and are used to obtain and transmit one or more sets of data to the transaction authentication information unit. The sets of data are associated with one or more performances of the authentication task by the user. The anomaly detector generates an authentication model using the one or more data sets transmitted to the transaction authentication information unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/039,019, filed Aug. 19, 2014, which is hereby incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

The present disclosure relates to implicit authentication systems for mobile devices.

BRIEF SUMMARY

In accordance with one embodiment, a system is provided for implicit authentication for a mobile device associated with a user, wherein the implicit authentication is behavioural, biometric and task-based and includes at least one authentication task selected so as to leverage the user's muscle memory. The mobile device comprises a touchscreen; a transaction authentication information unit; one or more sensors coupled to the transaction authentication information unit; and an anomaly detector coupled to the transaction authentication information unit. The sensors comprise (1) one or more touchscreen sensors coupled to the touchscreen, (2) an accelerometer, and (3) a gyroscope, and are used to obtain and transmit one or more sets of data to the transaction authentication information unit, the one or more sets of data being associated with one or more performances of the at least one authentication task by the user. The anomaly detector generates an authentication model using the one or more data sets transmitted to the transaction authentication information unit, the generating comprising constructing a set of features for a user profile associated with the one or more performances of the at least one authentication task, and one or more parameters associated with the set of features. The anomaly detector also performs training using the one or more data sets transmitted to the transaction authentication information unit, the training comprising learning so as to adjust the one or more parameters associated with the set of features, the learning being performed using one or more learning algorithms, and storing the user profile associated with the adjusted one or more parameters in the database. The anomaly detector also authenticates the user using the one or more data sets transmitted to the transaction authentication information unit, wherein the anomaly detector analyzes at least one of the one or more data sets corresponding to at least one of the one or more performances of the at least one authentication task using one or more anomaly detection algorithms together with the stored user profile. Based on the analyzing, the anomaly detector decides whether the authentication is successful or unsuccessful.

In accordance with another embodiment, a method is provided for implicit authentication for a mobile device associated with a user, wherein the implicit authentication is behavioural, biometric and task-based. The task-based behavioral biometric implicit authentication comprises at least one authentication task, and the authentication task is chosen so as to leverage the user's muscle memory. The mobile device comprises a touchscreen; a transaction authentication information unit; one or more sensors coupled to the transaction authentication information unit and comprising (1) one or more touchscreen sensors coupled to said touchscreen, (2) an accelerometer, and (3) a gyroscope; and an anomaly detector coupled to the transaction authentication information unit. The method comprises obtaining, by the one or more sensors, one or more sets of data associated with one or more performances of the at least one authentication task by the user; transmitting, by the one or more sensors, the obtained one or more sets of data to the transaction authentication information unit; generating, using the anomaly detector, an authentication model using the transmitted one or more data sets; and training the anomaly detector using the one or more data sets transmitted to the transaction authentication information unit,. The generating includes constructing a set of features for a user profile associated with the one or more performances of the at least one authentication task, and one or more parameters associated with said set of features. The training includes learning so as to adjust the one or more parameters associated with the set of features, the learning performed using one or more learning algorithms, and storing the user profile associated with the adjusted one or more parameters in the database. The anomaly detector authenticates the user using the one or more data sets transmitted to the transaction authentication information unit, by analyzing, by the anomaly detector, at least one of the one or more data sets using one or more anomaly detection algorithms together with the stored user profile; and deciding whether the authentication is successful or unsuccessful based on said analyzing.

The foregoing and additional aspects and embodiments of the present disclosure will be apparent to those of ordinary skill in the art in view of the detailed description of various embodiments and/or aspects, which is made with reference to the drawings, a brief description of which is provided next.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other advantages of the disclosure will become apparent upon reading the following detailed description and upon reference to the drawings.

FIG. 1 is a block diagram of a typical configuration of an authentication system for a mobile device.

FIG. 2 is a block diagram of a mobile device having a task-based behavioral biometric implicit authentication system.

FIG. 3 is a block diagram of a transaction authentication information unit.

FIG. 4 is a flowchart for a task-based implicit authentication system that uses swipes.

DETAILED DESCRIPTION

While the present disclosure is susceptible to various modifications and alternative forms, specific embodiments or implementations have been shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the disclosure is not intended to be limited to the particular forms disclosed. Rather, the disclosure is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of an invention as defined by the appended claims.

While the below description is written for mobile devices, it would be apparent to one having skill in the art that the embodiments described below could equally be applied to other user devices such as fixed or stationary devices and terminals as well.

Mobile devices such as smartphones, tablets and including wearable computing devices such as Google® Glass are vulnerable to being used by unauthorized individuals or impostors all the time. Whether it is a thief who steals it from a purse on a subway, a romantic partner checking text messages for signs of an affair, or a child looking to play games, mobile device users run serious risks when unauthorized users or impostors obtain access to such devices.

Various prior art and prior use mechanisms are utilized in mobile devices to protect against use by unauthorized individuals or impostors. For example, all smartphones have lock screens that are protected by a variety of mechanisms including PINs, passwords, gestures, and fingerprints. While lockscreens can provide significant protections when properly used, they can also degrade the usability of a device by inserting an unwanted step—the authentication step—between the user and their objective of using their phone at all times of the day and night. The burden is so significant that many users forego the protection of lock screens, as explained in “Beyond the pin: Enhancing user authentication for mobile devices” by S. Furnell, N. Clarke, and S. Karatzouni, Computer fraud & security, 2008(8):12-17, 2008; and “Authentication of users on mobile telephones—a survey of attitudes and practices” by N. L. Clarke and S. M. Furnell, Computers & Security, 24(7):519-527, 2005.

Even when users do enable these mechanisms, users may configure these mechanisms using weak credentials or so the device locks itself infrequently. Further, the protection provided is also incomplete, as some unauthorized users or impostors will know how to bypass the lock screen.

Implicit authentication mechanisms provide a solution to overcome these problems by allowing the mobile device to identify the user without the user doing any explicit authentication actions. Several researchers have proposed implicit authentication schemes for smartphones based upon how users interact with a touchscreen. Examples include the systems described in “Continuous mobile authentication using touchscreen gestures” by Feng et al, 2012 IEEE Conference on Technologies for Homeland Security (HST), pp. 451-456, 2012; and “Touchalytics: On the applicability of touchscreen input as a behavioral biometric for continuous authentication” by Frank et al, IEEE Transactions on Information Forensics and Security, vol. 8, no. 1, pp. 136-148, 2013. Systems such as the one described in “Behaviomobile: Applying the behaviosec technology for multilayered mobile security”, retrieved from http://behaviosec.com/wp-content/uploads/2012/10/whitepaper-behaviomobile.pdf attempt to ensure that the correct person is entering a password pattern or a Personal Identification Number (PIN).

Other schemes have been proposed based on how users hold the phone, such as the system described in “A new non-intrusive authentication method based on the orientation sensor for smartphone users” by C.-C. Lin, D. Liang, C.-C. Chang, and C.-H. Yang in 2012 IEEE Sixth International Conference on Software Security and Reliability (SERE), pages 245-252. IEEE 2012.

Other schemes have been proposed based on gait, such as the system described in Derawi, Mohammad Omar, et al. “Unobtrusive user-authentication on mobile phones using biometric gait recognition.” Intelligent Information Hiding and Multimedia Signal Processing (IIH-MSP), 2010 Sixth International Conference on. IEEE, 2010.

To date, however, commercially available prior art and prior use systems have offered only improved security guarantees, such as by ensuring the correct person is entering a PIN or password pattern, rather than the improved usability of a non-intrusive authentication system.

While results from these prior art systems show that it is possible to distinguish users using mobile device sensors and machine learning algorithms, these prior art systems do not use appropriate algorithms or the appropriate evaluation methodologies that are required for building and assessing a workable implicit authentication scheme.

There are several requirements for practical mobile device implicit authentication mechanisms, which will be discussed in the section titled “Requirements” below.

A swipe-based implicit authentication scheme that addresses the requirements is then set out in the section titled “Approach”.

Prior Art Approaches to Mobile Authentication

FIG. 1 illustrates a typical configuration for a mobile device. A mobile device such as mobile device 101 is coupled to network 102 using at least one communication technique known to those of skill in the art. Examples of communication techniques include Wi-Fi, LTE, 2G and 3G. A fraud reporting center 103 and an authentication server 104 are also coupled to the mobile device 101 via a network 102 that is is implemented using one or more networking technologies known to those of skill in the art. Examples of these networking technologies include wired networks, wireless networks, optical networks, Local Area Networks (LAN), Campus Area Networks (CAN) and Metropolitan Area Networks (MAN). In some embodiments, network 102 is comprised of a plurality of networks and subnetworks.

Following the example of lock screens in desktop-oriented operating systems, mobile devices all include, at the very least, a text-based authentication option. Several factors specific to mobile devices make text-based authentication less usable and secure than on desktop or notebook computers. For example, modern smartphones primarily employ touch-based on-screen keyboards that require switching between multiple screens in order to access infrequently used characters and use text prediction to improve typing accuracy. Good passwords, however, are long strings of characters that cannot be easily predicted and include multiple infrequently used characters. Secure passwords are thus hard to enter on smartphones.

PINs are simpler to enter due to the larger, and fewer, buttons that are needed, and their shorter length. However, they are still not as easy to enter as on a physical keyboard. Furthermore, they are particularly easy for an attacker or impostor to observe, given their simplistic nature, by “shoulder surfing” or taking a video of a person typing in their PIN. Shoulder surfing is a significant problem as mobile devices are heavily used in public environments, places where an attacker/impostor can more easily observe PIN entry and steal a device.

A number of different approaches have been proposed to reduce the usability strain of text-based authentication mechanisms on mobile devices while maintaining high security. One popular alternative is a swipe pattern unlock screen, such as the standard Android pattern unlock interface. In the Android implementation, the password is an ordered series of connected points which the user connects by dragging their finger on the screen. While this is a usability improvement over text entry, the approach is still vulnerable to shoulder surfing by impostors, smudge attacks by impostors, as well as random guessing of common patterns.

Other solutions such as “SkipLock” created by B. Hirashima and described at http://benhirashima.com/skiplock/, retrieved Jun. 19, 2014, have focused on avoiding the use of authentication mechanisms by establishing trusted areas where the identity of the user can be established with high probability based on their location. For example, a user may configure their device to never ask for a password when it is within their home, which may be established by GPS coordinates, or when it is near a trusted computer, which could be determined via Bluetooth. Though this approach does increase usability by bypassing authentication in tightly bounded scenarios, it does nothing to increase either the usability or the security of authentication in public settings. Furthermore, it also does not help with the numerous non- traditional impostor attacks mobile devices are subject to, for example, a child playing a game on a parent's work phone or tablet.

Moving away from the traditional approaches to authentication described above, biometrics have become an increasingly popular mobile authentication mechanism, especially in the past year with the introduction of fingerprint identification to Apple® iOS® Security and more recently Samsung smartphones, such as described in http://www.samsung.com/global/microsite/galaxy5/features.html retrieved Jun. 19, 2014.

Many biometric approaches use static biometrics, in that they are based upon one or more characteristics of the human body that remains stable over time. For example, fingerprint scanners; facial recognition systems such as that described in http://www.android.com/about/ice-cream-sandwich/ retrieved Jun. 19, 2014; and eye scan-based authentication mechanisms such as that described in “EyeVerify. White Paper: Third-Party Verification of Eyeprint Accuracy,” April 2013 are all commercially available for smartphones. Static biometrics generally have high true positive rates (authorized users can easily unlock the device) and high true negative rates (unauthorized users are rejected).

There are two fundamental limitations of static biometrics, however. The first is that static biometric approaches require that the user take explicit action to authenticate themselves by exposing some part of their anatomy to a sensor. Such an explicit action will, in general, be a distraction from the user's primary task, and as such frequent authentication checks will be unacceptable to most users. The second is that static biometrics can often be mimicked by impostors using relatively simple techniques known to those of skill in the art, for example, a picture of a person's face to fool a facial recognition sensor; or a latex finger to subvert a fingerprint scanner. This mimicry is fundamentally hard to stop because the primary sensor used is, essentially, a camera, and there are many ways of fooling cameras, and there are many ways of obtaining a copy of the original person's biometric data, for example, gathering fingerprints left elsewhere on a device.

Furthermore, some static biometrics may persist even when the user has either been killed or seriously injured by an impostor, such as, for example, retina scans and fingerprint authentication. Liveness detection, such as checking for blinking in an image while doing facial recognition, are, in practice, insignificant barriers to attackers because these sensors can also be defeated using means known to those of skill in the art such as described in http://www.androidpolice.com/2012/08/03/android-jelly-beans-face-unlock-liveness-check-circumvented-with-simple-photo-editing/.

While mimicry attacks against static biometrics is a concern, of greater concern are the extra steps required for authentication using static biometrics. Explicit authentication actions, no matter how simple, introduce friction that users will want to minimize, if not eliminate. A trade-off for lower security is often perceived as being worth the cost, at least until a device is compromised.

Behavioral Biometrics

Biometrics in general distinguish users based upon invariants in “who they are.” As previously discussed, static biometrics are based upon invariants in physical characteristics. Dynamic biometrics, or more commonly behavioral biometrics, are based upon invariants in an individual's behavior. Generally this behavior is consistent because of subconscious factors affecting how human bodies operate. While some schemes are based upon characteristics that are primarily involuntary, such as

-   -   Heartbeats, as described in “Analysis of human electrocardiogram         for biometric recognition” by Y. Wang, F. Agrafiooti, D.         Hatzinakos, and K. N. Plataniotis in EURASIP journal on Advances         in Signal Processing, 2008:19, 2008; and     -   Neural signals and other brain activity recorded in response to         a specific visual or auditory stimulus using a system such as         the ones described in “Pass-thoughts: authenticating with our         minds” by J. Thorpe, P. C. van Oorschot, and Anil Somayaji in         Proceedings of the 2005 workshop on New security paradigms (NSPW         '05). ACM, New York, N.Y.; and “Biometrics from brain electrical         activity: a machine learning approach” by R. Palaniappan         and D. P. Mandic in Pattern Analysis and Machine Intelligence,         IEEE Transactions on, 29(4):738-742, 2007 .         Most are based upon behavior that is under more conscious         control.

Behavioral biometrics can be grouped into three categories: continuous, secondary and task-based. With a continuous behavioral biometric, the behavior of the user is continually observed and modeled, with the system detecting abnormal usage patterns associated with unauthorized use on an ongoing basis. With secondary biometrics, user behavior is monitored only while performing a standard authentication task, such as a PIN entry. A task-based biometric is similar in spirit to a secondary biometric, except that any task can be observed and modeled, not just an explicit authentication task.

Behavioral biometrics are, in general, more challenging to develop and deploy than static biometrics because human behavior is fundamentally variable. Despite this, the accuracy can be comparable to that of static biometrics-based systems because behavioral biometrics can take advantage of many more observations than static biometrics, and can do so in ways that require no additional work from the user.

Behavioral biometrics have a long history, including, for example,

-   -   Keyboard typing patterns such as the system described in         “Keystroke dynamics as a biometric for authentication” by F.         Monrose and A. D. Rubin in Future Generation computer systems,         16(4):351-359, 2000;     -   Facial recognition such as the system described in “Face         recognition: A literature survey” by W. Zhao, R.         Chellappa, P. J. Phillips, and A. Rosenfeld in ACM Computing         Surveys (CSUR), 35(4):399-458, 2003; and     -   Handwriting recognition such as the system described in “Online         and off-line handwriting recognition: a comprehensive survey”         by R. Plamondon and S. N. Srihari in Pattern Analysis and         Machine Intelligence, IEEE Transactions on, 22(1):63-84, 2000.

However there is a need to focus on behavioral biometrics that are easily observed during the course of normal smartphone usage, specifically behavioral biometrics that utilize three key smartphone sensors: the touchscreen, the accelerometer and the gyroscope.

Requirements

In this section, five key requirements seen as being essential to a secure and usable implicit authentication solution are detailed.

(1) Learn only on user data: While it is possible to get samples of simulated malicious behavior in a lab setting, a deployed behavioral biometric system will not have access to representative malicious behavior. It also won't have access to a representative set of other user behavior, except perhaps for offline tuning purposes. Thus a behavioral biometric should construct its model of a user's behavior based primarily (if not exclusively) on observations of that user. In machine learning terms, anomaly detection algorithms or one-class learning algorithms must be used. Many commonly-used machine learning algorithms are two or multi-class learning algorithms and therefore do not meet this requirement.

(2) Model stable observables: Within the framework of anomaly detection, it is easier to learn normal behavior if the space of possible behaviors is small. In the context of smartphones this requirement is challenging as smartphone sensors may produce a deluge of data. Further, the output of these sensors can be highly variable: for example, they vary widely depending upon the task the user is performing: navigation while driving, a tilt-controlled game, or email. In machine learning, the “curse of dimensionality” says that as the complexity of data increases, the more data is required in order to learn a model. For implicit authentication quick learning of models of user behavior and quick detection of anomalies are important. Effective implicit authentication systems, then, will filter or process their data such that they detect anomalies in “stable observables”—characteristics of the data which remain invariant, unique and act predictably over time. This points to a disadvantage of continuous behavioral biometrics, as these systems will have less stable observables than secondary and task-based ones, simply because continuous gathering of user behavior will inevitably mean the system will be observing the user is highly variable contexts. Therefore, known consistent phenomena which will generally produce consistent data for modeling purposes should be used.

(3) Employ lightweight, online learning algorithms: User behavior is expected to naturally change over time. Anomaly detection algorithms thus must run online so that they can constantly learn from newly observed behavior. This incremental online learning must also be computationally lightweight as it should not impose significant latency upon the user interface—the user should not have to wait for the device to decide whether an action is going to be allowed or not. Lightweight learning methods are made feasible by stable observables: the easier the learning problem, the simpler the method that can achieve good results.

(4) Be resistant to mimicry attacks: Mobile devices such as smartphones are often used in public places, where they may be lost or stolen. This means that mobile devices must consider an attack scenario not commonly considered in other authentication contexts, that is where an attacker or impostor is able to physically observe the authentication taking place. For this reason it is important for implicit authentication schemes to be resistant to mimicry, or imitation, attacks. A typical “something you know” authentication scheme, such as a pin or password, performs poorly on this metric, since the attacker/impostor observes the credential being inputted and is able to replicate it perfectly. Though shoulder surfing resistant mitigation techniques exist such as those described in “Shoulder surfing defence for recall-based graphical passwords” by N. H. Zakaria, D. Griffiths, S. Brostoff, and J. Yan in Proceedings of the Seventh Symposium on Usable Privacy and Security, page 6. ACM, 2011; these mitigation techniques typically gain this increase in security by compromising usability.

(5) Authentication should be non-intrusive: Security is almost always a secondary task for users. This means that it distracts from the main activity the user wants to accomplish, for example checking their email or responding to a text message. This is particularly true of authentication, which inserts itself directly between the user and the task they want to accomplish. One way to make authentication usable is to ensure it is non-intrusive—meaning that it is transparent to the user. An example of a transparent authentication system in a non-mobile context are SSH public keys. Rather than prompting the user to enter an explicit password when connecting to an SSH server, the system uses public key cryptography to automatically establish the user's identity. In a mobile context, an explicit authentication task such as entering a PIN or password is intrusive, hence the frequency of authentication requests must be minimized, for example, only performed when the device is woken up from sleep after 5 minutes of inactivity. Because secondary biometrics require explicit authentication actions such as PIN entry, these are considered to be relatively intrusive. In contrast, continuous and task-based behavioral biometrics tend to be non-intrusive.

Prior Art Behavioral Biometric Systems

Early works of prior art in behavioral biometrics-based implicit authentication in a mobile context are the systems described in:

-   -   “Implicit authentication for mobile devices” by M. Jakobsson, E.         Shi, P. Golle, and R.

Chow in Proceedings of the 4th USENIX conference on Hot topics in security, pages 9-9, USENIX Association, 2009; and

-   -   “Implicit authentication through learning user behavior” by E.         Shi, Y. Niu, M. Jakobsson, and R. Chow in Information Security,         pages 99 {113. Springer, 2011.

In these works, systems based on implicit authentication via observation of user behavior are described. These works model user behavior as the probability of seeing a particular event, such as a phone call to a certain number, conditioned on the time of day. This model is used to calculate an authentication score, which triggers a security event if the score drops below a threshold. The modeling is built only on observation of user data, which satisfies the first requirement above. However, since this is a continuous system, the space of user behavior is large and may not be stable. Additionally, since attack scenarios are tested by splicing data from other users into one user's data stream; thus they only test whether users can be distinguished, not whether they can imitate each other. Therefore it is unclear whether such a system is resistant to mimicry attacks by impostors.

In the system described in “Progressive authentication: deciding when to authenticate on mobile phones” by O. Riva, C. Qin, K. Strauss, and D. Lymberopoulos in Proceedings of the 21st USENIX Security Symposium, 2012, the motivation is to reduce the number of times a user is asked to authenticate. This is done by combining a number of sensors to establish a confidence that the device is in the possession of the correct user. For example, the microphone can be leveraged to do voice recognition, Bluetooth can be used to establish if the phone is near another trusted device, the camera is available for facial recognition, and more. Some of these tasks constitute stable observable tasks according to the second requirement. However, training some sensors, such as facial or voice recognition, is an inefficient and obtrusive task. Additionally, the system divides access to content on the device into three different security levels. More confidential content requires a higher confidence to access without explicit authentication than less confidential content. The system uses support vector machines (SVM) and decision tree models which train on multiple classes of user data, thus they do not meet our first requirement. Though the evaluation does include attack scenarios, the scenarios do not include scenarios concerning imitation by impostors. Therefore it is unclear whether such a system is resistant to mimicry attacks.

Other work which continues along the same lines is the system described in “Senguard: Passive user identification on smartphones using multiple sensors” by W. Shi, J. Yang, Y. Jiang, F. Yang, and Y. Xiong in Wireless and Mobile Computing, Networking and Communications (WiMob), 2011 IEEE 7th International Conference on, pages 141-148. IEEE, 2011, which aims to incorporate touch gesture recognition along with voice, gait and location information to identify users in a continuous way. The system uses one-to-many binary classifiers, which do not train only on user data and therefore does not meet the first requirement. These classifiers also cannot be updated continuously, which impacts their ability to learn efficiently. Since observation seems to be occurring at all times, it is difficult for the system to achieve stable observation. However the system does not consider imitation attacks by impostors, so therefore it is unclear whether such a system is resistant to mimicry attacks.

While the previously mentioned work performs continuous authentication by fusing data from multiple sensors together to make an authentication decision, other systems take a narrower focus. The system described in “Continuous mobile authentication using touchscreen gestures” by Feng et at in IEEE Conference on Technologies for Homeland Security (HST), pp. 451-456, 2012 uses touch information from the user performing common gestures combined with data from a sensor glove the user wears to discriminate between users. This system relies on classification algorithms such as decision trees and random forests, which do not train solely on a single class of user data. The evaluation does not include an analysis of imitation attacks by impostors, therefore it is unclear whether such a system is resistant to mimicry attacks. Furthermore, the best results were obtained using information from a specialized glove worn by the user to collect additional data, which appears intrusive.

The system described in “A new non-intrusive authentication method based on the orientation sensor for smartphone users” by C.-C. Lin, D. Liang, C.-C. Chang, and C.-H. Yang in Software Security and Reliability (SERE), 2012 IEEE Sixth International Conference on, pages 245-252. IEEE 2012 takes a similar approach. However the system focuses exclusively on the orientation of the device as the user performs a touch screen gesture, the hypothesis being that users hold their devices in a unique way. The training set for each user contains 450 samples, which is not conducive to fast learning. Since the system is not tested against imitation attacks by impostors, it is unclear whether such a system is resistant to mimicry attacks. However, the system does train only on a single class of user data, and authentication does occur transparently to the user.

The system described in “Silentsense: silent user identification via touch and movement behavioral biometrics” C. Bo, L. Zhang, X.-Y. Li, Q. Huang, and Y. Wang in Proceedings of the 19th annual international conference on Mobile computing & networking, pages 187-190. ACM, 2013 combines both touch behavior and small movements in the accelerometer and gyroscope over the course of a touch gesture to try and identify when a guest is using the device, which is not intrusive for the user. The system observes sequences of gestures to determine whether a new user is using the device. The system uses both one class and multi class learning, partially fulfilling the first requirement. However, monitoring occurs continuously during the operation of applications, which may not be a stable observable. Again, the use of multi-class learning impacts the ability of the algorithm to efficiently learn. The evaluation does include attackers or impostors using a legitimate user's device, however these are not explicitly imitation attempts—rather they are random attackers/impostors who do not have knowledge of the user's behavior. Therefore it is unclear whether such a system is resistant to mimicry attacks.

The system described in “Touchalytics: On the applicability of touchscreen input as a behavioral biometric for continuous authentication” by Frank et al, IEEE Transactions on Information Forensics and Security, vol. 8, no. 1, pp. 136-148, 2013 considers the characteristics of the touch gesture itself, extracting and analyzing features such as the velocity, starting and ending locations, and direction. The system uses authentication after observation of a single swipe, as well as after observation of a sequence of swipes. The work employs classification techniques which do not train solely on user data and which impact learning efficiency. Again, observation is continuous, and so may not be stable.

Approach

A decision as to whether to use a continuous, secondary, or task-based biometric as an implicit behavioral biometric must be made. Secondary biometrics require an intrusive, primary authentication action, thus they are not a good candidate for implicit authentication. As seen in the previous section, continuous behavioral biometrics suffer from two issues. First, given the nature of continuous monitoring, one must deal with a large, dynamic state space produced by the output of multiple sensors. This results in a highly complex, multi-modal data landscape that is very challenging to model as it changes with context. For example, if the user starts playing a game on their phone, then the data obtained may be very different from the case where the user is answering emails.

Therefore a task-based behavioral biometric implicit authentication scheme best meets the requirements set out previously. Task-based behavioral biometric implicit authentication schemes leverage the muscle memory users build up doing a common task. The more habitual the task, the more likely it will be to characterize normal behavior, and consequently, the easier it will be to detect anomalies. Also, it makes it harder to imitate thus making it more resistant to mimicry attacks.

A natural candidate task for a task-based behavioral biometric on a smartphone is by modeling standard user interactions with the device. Smartphone interfaces since the iPhone® are designed around a variety of multi-touch gestures such as taps, pinches, and swipes. Most of these interactions involve on-screen widgets that present one or more specific touch targets to the user, such as buttons, sliders, scrollable lists, and so on.

One would expect significant variability in how the widget is used based upon its context in the application. Factors such as where a button is placed, or the number of items in a scrollable list, could affect the pattern of how a user interacts with a widget. To maximize the likelihood of uniform interface interactions, a task that minimizes these variations must be chosen.

One possibility would be to authenticate users based on their typing patterns on an on-screen keyboard such as described in “Authenticating mobile phone users using keystroke analysis” by N. L. Clarke and S. Furnell in International Journal of Information Security, 6(1):1-14, 2007. However, typing is not an appropriate task to consider for task-based authentication on a smartphone. This is because typing is so arduous that the entire interface of the device is designed to minimize the use of an on-screen keyboard; furthermore, significant variations in typing behavior are expected depending upon what is being typed, and for what purpose. Thus, in order to get better performance and usability characteristics, an action that is more common than typing on smartphones, and also displays high levels of regularity is required.

One such habitual task which is used is one or more swipes or swipe gestures. A swipe is the horizontal sliding away of a screen. Whether slid to the left or to the right, such screen transitions are common: they are used to present cover screens (as with the iOS lockscreen) and to present multiple information screens. In some embodiments, the permissibility of a swipe gesture is made clear through visual cues or explicit visual indicators such as dots at the bottom of a screen, where each dot indicates a screen that can be viewed. In other embodiments, swipes have no explicit visual indicator. An example of this is an Really Simple Syndication (RSS) reader where swipes transition between items.

Because of the common usage of swipes, users readily develop subconscious muscle memory. For example, readers can swipe without knowing when reading an electronic book. Furthermore users tend to perform swipes in a user-specific way. This makes it harder to imitate the performance of these tasks thus making such a system more resistant to mimicry attacks. Swipes also have the advantage of offering no specific touch targets. Generally, swipes offer flexibility to users as well, as many different kinds of swipes all produce the same results. Therefore swipes are good candidate tasks for task-based behavioral biometric implicit authentication on a mobile device.

FIGS. 2-4 illustrate an embodiment of a task-based behavioral biometric implicit authentication system using swipes.

FIG. 2 shows a detailed embodiment of the mobile device 101 of FIG. 1 having a transaction authentication information unit 201 coupled to a graphical user interface 202, a communication interface 203, a Global Positioning System unit 204, an environment unit 205, a key login speed unit 206, an accelerometer 207, a gyroscope 208, and one or more touchscreen sensors 209 coupled to a touchscreen on a mobile device.

The graphical user interface 202 provides the user with the ability to enter and view information and includes a keyboard and display for example. The communications interface 203 allows the mobile device to communicate with other devices and servers in a network communications system.

Components 204-209 are one or more sensors which provide data to the transaction authentication information unit 201. The GPS unit 204 provides position and velocity information. The environment unit 205 provides information on environmental conditions such as temperature, humidity and wind speed. The key login speed unit 206 monitors the speed at which login information is keyed in. The accelerometer 207 and gyroscope 208 provide information such as orientation of the mobile device, velocity of the mobile device and acceleration of the mobile device, which can then be used to calculate, for example, distance travelled by the mobile device and direction taken by the mobile device. It is known to one of skill in the art that these may not be the only sensors coupled to the transaction authentication information unit. For example, in some embodiments, biometric sensors such as heartbeat detectors, fingerprint detectors and body temperature detectors are also connected to the mobile device and transaction authentication information unit 201. Touchscreen sensors 209 are coupled to the touchscreen to capture data from user interaction with the touchscreen. Examples of touchscreen sensors include pressure sensors to detect force on the touch screen of a smartphone or tablet. An example of such a sensor is described in, for example, “Apple Patents IR Tech For Detecting The Force Of Touch Input On iPads And iPhones” posted Apr. 3, 2014 and retrieved from http://techcrunch.com/2014/04/03/apple-patents-ir-tech-for-detecting-the-force-of-touch-input-on-ipads-and-iphones/ on Apr. 9, 2014 and herein incorporated by reference as if reproduced in its entirety. The sensor and technology underlying the sensor is further described in detail in US Patent Application 2014/0092052 to Grunthaner et al herein incorporated by reference as if reproduced in its entirety. In a further embodiment, the sensors are built into the touchscreen.

The transaction authentication information unit 201 communicates with the various components and sensors 202-209 to receive data on the mobile device and to perform authentication. For example, the transaction authentication information unit 201 communicates with the GPS unit 204 to receive position and velocity information for the mobile device. The environment unit 205 communicates with transaction authentication information unit 201 to receive information on environmental conditions at the location of the mobile device. In addition, the transaction authentication information unit 201 communicates with the key login speed unit 206 to receive information on key logins. The transaction authentication information unit 201 communicates with the accelerometer 207 and the gyroscope 208 to receive information to, for example, determine velocity and acceleration of the user/device. This can be used to, for example, determine gait of the user. The transaction authentication information unit 201 communicates with the GUI 202 to provide a GUI for displaying information relevant to the authentication process and for user input of information required for input by the user.

The transaction authentication information unit 201 is implemented using, for example, hardware, software, or a combination of hardware and software. FIG. 3 illustrates an embodiment of the transaction authentication information unit 201 that includes an anomaly detector 301 that operates and configures one or more anomaly detection algorithms. Anomaly detector 301 also builds and configures one or more user models. The anomaly detection algorithms together with the user models or user profiles are utilized by the anomaly detector 301 to authenticate the user. The user models or user profiles are stored within transaction authentication information unit 201 in database 302. Each of anomaly detector 301 and database 302 are implemented using, for example, hardware, software or a combination of hardware and software.

FIG. 4 is a flowchart for a task-based implicit authentication system that uses swipes. In step 401, in one embodiment, an authentication model for swipes is generated using data from one or more sensors. In an embodiment, to generate an authentication model for swipes, data from the accelerometer 207, the gyroscope 208, and the touch screen sensors 209 are obtained and sent to transaction authentication information unit 201. The first two sensors return three distinct time series, one for each axis. These time series represent the motion of the mobile device in 3-dimensional space while the swipe is being performed across the touchscreen. The touch screen sensors return two time series representing the x- and y-coordinates of points on the swipe. The pattern of each of these time series is likely to be unique among users. In one embodiment, in step 401 the accelerometer, gyroscope and touchscreen sensor time series data for each swipe is discretized by the anomaly detector 301 by binning and calculating the area and slope of the data in each bin, after the data is obtained from these one or more sensors.

These time series data is then used by the anomaly detector 301 running on transaction authentication information unit 201 to construct a set of features with associated model parameters to be stored in the user profile in order to represent a swipe. This further increases the strength of the authentication system because: Unlike fingerprints, for example, only a feature representation of the swipe is stored in the user profile and not the entirety of the swipe data. This makes it more difficult for an impostor to re-engineer this set of features with associated model parameters to recreate the original swipe and hence defeat the system.

In one embodiment, the set of features associated with a swipe are represented by one or more of:

-   -   (1) start and end co-ordinates,     -   (2) swipe direction,     -   (3) duration of the swipe,     -   (4) length of the swipe,     -   (5) the peak length and duration.         The pattern of each of these time series is likely to be unique         among users. Then, the swipes are thus represented by a feature         vector consisting of these values.

In one embodiment, in step 402 the anomaly detector 301 performs training, that is the anomaly detector 301 learns how the user performs the task so as to distinguish between the user and an impostor, and consequently improve resistance to mimicry attacks. In one embodiment, the learning is performed based on the data received from the one or more sensors. Then, learning is performed using the time series data. In another embodiment, the discretizing process previously described is performed using the time series data received from the one or more sensors. Then, learning is performed using the discretized time series data. In an embodiment, the anomaly detector 301 performs the learning so as to adjust the model parameters associated with the set of features described above. In one embodiment, one or more learning algorithms are used to adjust the model parameters.

The amount of data required to train the detector 301 is an important parameter. Making the user swipe a large number of times to train the detector will greatly reduce its convenience factor. In one embodiment, a number of swipes are used as the initial training window and authentication is begun after the last swipe. In a further embodiment, in order to ensure that the system is up-to-date with the user's swipe patterns, a rolling window approach to training is employed, in which the latest authenticated swipe is added to the training window, and the earliest swipe is removed. Then training is performed using the data sets corresponding to the remaining swipes within the training window.

As explained previously, a feature vector is used to represent the swipes. An exemplar feature vector is generated from all the swipes in the training window by the anomaly detector 301 by calculating the average of the feature vector values. In one embodiment, the mean and standard deviation of the distances of the feature vectors corresponding to the swipes in the training window from the exemplars are calculated.

In a further embodiment, the user's behavior is modelled using their global maximum and minimum values in each axis for each sensor. For a given axis i, the maximum and minimum values are obtained by calculating the mean, μ_(si) and standard deviation, σ_(si) of sensor s. The maximum and minimum are then calculated as:

max_(si)=μ_(si) +kσ _(si)

min_(si)=μ_(si) −kσ _(si)

where k is a threshold. In yet another embodiment, k is a user specified parameter.

In a further embodiment, in step 402, in one embodiment, the one or more learning algorithms comprise comparing the user's performance of the task with impostor or attacker attempts to imitate the user's performance of the task. In a further embodiment, a plurality of attacker/impostor models, each having one or more corresponding characteristics, is created and stored in, for example, database 302 of transaction authentication information unit 201 to enable the comparison. Examples of such attacker/impostor models have been developed in the context of email system authentication in Li, Yiru et at “Securing email archives through user modeling.” Computer Security Applications Conference, 21st Annual. IEEE, 2005; and Li, Yiru. “Toward Email Archive Intrusion Detection.” Master of Computer Science dissertation, Carleton University, 2005; both herein incorporated by reference as if reproduced in their entirety. In a further embodiment, at least one of these models are then used to set the thresholds mentioned above, and make sure that the thresholds for a user are not so large as to allow malicious attacks. In a further embodiment, at least one of the attacker models are based upon empirically-derived observations of the ability of one or more people other than the user to imitate the user's actions. In another embodiment, at least one of the models are based on one or more estimates of the capabilities of hypothetical impostors. These estimates can be obtained via, for example, simulations.

The user profile with the adjusted parameters is stored in database 302 of the transaction authentication information unit 201. By using known data from the user to build a model that best captures the intricacies of that data in step 402, this satisfies the requirement of learning using user data. It is important that the model parameters are not too tight or specific, as that will not allow the user to be authenticated; or too loose or general, as that will allow attackers to be authenticated.

In step 403, the user is prompted to perform the task and is authenticated based on the performance of the task. In step 403, anomaly detector 301 utilizes one or more anomaly detection algorithms together with the stored user profile created in step 402 to authenticate the user. Specifically, the anomaly detector analyzes the data received from the one or more sensors associated with the performance of the task, and compares the analyzed data to the stored user profile using the anomaly detection algorithms. Based on this analysis, the anomaly detector makes an authentication decision, that is, the anomaly detector indicates whether the authentication is successful or unsuccessful.

For example, in the embodiment where mean and standard deviation are used, swipes are authenticated if their distance from the exemplar is within a threshold number of standard deviations of the mean. In one embodiment, the threshold number is a user specified parameter.

In the embodiment where the user's behavior is modelled using their global maximum and minimum values in each axis for each sensor: If the swipe falls within said [min_(si), max_(si)] range, the user is authenticated.

In a further embodiment, the anomaly detector 301 produces a boolean output based on the authentication analysis, that is either a TRUE or a FALSE is produced. corresponding to whether the authentication is successful or unsuccesful. In another embodiment, the anomaly detector produces a score indicating the likelihood that the person performing the task for authentication is the user and not an impostor based on the result of the authentication. If the score is above a threshold then the anomaly detector indicates the authentication is successful. If the score is below a threshold, then the anomaly detector indicates that the authentication is unsuccessful.

In one embodiment, the task to be used for authentication is combined with one or more non-authentication tasks which do not form part of the authentication. For example, as part of the authentication mechanism, the user may be asked to read a plurality of pages of text, zoom in on specific parts of each page, and transition between pages by swiping. However steps 402 and 403 are performed only for the swipes. This way, the user does not realize which tasks are being used for authentication purposes. Such an arrangement improves security, because if a user does not realize which tasks are being used for authentication purposes, the likelihood of an impostor knowing which tasks are being used for authentication is reduced.

In another embodiment, a combination of different tasks is used for authentication. For example, in one embodiment, the combination comprises two tasks. The first task is performing one or more swipes. A second task is performing one or more zoom gestures. Then, in one embodiment, steps 401-403 are performed for each of the tasks within the combination of tasks.

While the above describe embodiments where authentication is implemented within the mobile device, other embodiments are also possible. In another embodiment, authentication is implemented using a cloud-based service. An example of such an implementation is explained below with reference to the components of FIGS. 1 and 2. Mobile device 101 runs an application or an “app.” As part of the operation of the app, the transaction authentication information unit 201 receives data from one or more sensors such as sensors 204-209 of the mobile device, and forwards the information obtained from the one or more sensors to, for example, fraud reporting center 103 or authentication server 104 over network 102. Instead of running on transaction authentication information unit 201, the anomaly detector runs at the fraud reporting center or the authentication server to perform steps 401-403 of FIG. 4. The anomaly detector takes the data transmitted from the transaction authentication information unit 201 as an input, and uses one or more anomaly detection algorithms together with a user profile to authenticate the user. The user profile is stored within a database located at the fraud reporting center 103 or within the authentication server 104.

In another embodiment, the anomaly detector is implemented in a distributed fashion over the mobile device 101 and the fraud reporting center 103 or authentication server 104. The user profile is stored within a database located within the mobile device 101, or at the fraud reporting center 103, or within the authentication server 104. Then, the anomaly detector to perform steps 401-403 of FIG. 4, that is, it retrieves the user profile, and uses one or more anomaly detection algorithms together with the user profile to authenticate the user.

In one embodiment, if the authentication in step 403 fails due to the detection of anomalous performance by the anomaly detector, then the anomalous performance is reported to, for example, the authentication server 104 or the fraud reporting centre 103 over network 102. Data associated with the anomalous performance such as the nature of the anomaly, time, and other information about the state of the device such as the application that was running and the device's location is stored in, for example, a database located in the fraud reporting center 103 or authentication server 104.

While the above describes embodiments which use data generated by accelerometer 207, gyroscope 208 and touchscreen sensors 209, it would be known to one of skill in the art that data from any of the sensors 204-209 can be used.

In another embodiment, the data obtained from the one or more sensors can be combined with contextual data to perform steps 401-403. Contextual data refers to data associated with the context of the user. Examples of contextual data include:

-   -   the location of the user,     -   the weather at the location of the user,     -   the time of day,     -   whether the user is standing, sitting, running, walking or         sleeping, or     -   whether the user is within a moving vehicle.

Contextual data can be obtained from a variety of sources, including, for example, the one or more sensors connected to the mobile device 101, the fraud reporting centre 103 and the authentication server 104. In one embodiment, steps 402 and 403 are adjusted based on the 4819-9304-7335.1 contextual data obtained. For example, if a user has been running, it is likely that the swipes performed by the user will be different to the swipes performed by the user when the user is sitting down. Then the anomaly detector configures steps 402 and 403 so that it is able to learn and distinguish between the swipe performances for these different situations.

In another embodiment, contextual data can be used to assign a trust level for use in step 403. For example, in one embodiment, a trust level is assigned based on user location, that is, when the user is in a high trust location such as a home, a high trust level is assigned. When the user is in a public location, lower trust levels may be assigned based on the location. For example, if the user is in a location which is known to have many potential impostors, a lower trust level is assigned. Then, for example, step 403 includes performing additional tasks for authentication which the user does not realize are being used for authentication. The assigning is performed by, for example, the anomaly detector or transaction authentication information unit 201.

In yet another embodiment crowdsourced data is used, either solely or in combination with the contextual data, to assign the trust level. Crowdsourced data is obtained from a variety of sources, for example, social media sites, microblog sites and input from one or more users. For example, based on information scoured from one or more social media sites or specifically peer-to-peer interactions on the one or more social media sites, the anomaly detector or transaction authentication information unit 201 assigns different levels of trust to different locations.

Although the algorithms described above including those with reference to the foregoing flow charts have been described separately, it should be understood that any two or more of the algorithms disclosed herein can be combined in any combination. Any of the methods, algorithms, implementations, or procedures described herein can include machine-readable instructions for execution by: (a) a processor, (b) a controller, and/or (c) any other suitable processing device. Any algorithm, software, or method disclosed herein can be embodied in software stored on a non-transitory tangible medium such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), or other memory devices, but persons of ordinary skill in the art will readily appreciate that the entire algorithm and/or parts thereof could alternatively be executed by a device other than a controller and/or embodied in firmware or dedicated hardware in a well known manner (e.g., it may be implemented by an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic device (FPLD), discrete logic, etc.). Also, some or all of the machine-readable instructions represented in any flowchart depicted herein can be implemented manually as opposed to automatically by a controller, processor, or similar computing device or machine. Further, although specific algorithms are described with reference to flowcharts depicted herein, persons of ordinary skill in the art will readily appreciate that many other methods of implementing the example machine readable instructions may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined.

It should be noted that the algorithms illustrated and discussed herein as having various modules which perform particular functions and interact with one another. It should be understood that these modules are merely segregated based on their function for the sake of description and represent computer hardware and/or executable software code which is stored on a computer-readable medium for execution on appropriate computing hardware. The various functions of the different modules and units can be combined or segregated as hardware and/or software stored on a non-transitory computer-readable medium as above as modules in any manner, and can be used separately or in combination.

While particular implementations and applications of the present disclosure have been illustrated and described, it is to be understood that the present disclosure is not limited to the precise construction and compositions disclosed herein and that various modifications, changes, and variations can be apparent from the foregoing descriptions without departing from the spirit and scope of an invention as defined in the appended claims. 

What is claimed is:
 1. A system for implicit authentication for a mobile device associated with a user, wherein the implicit authentication is behavioural, biometric and task-based and includes at least one authentication task selected so as to leverage the user's muscle memory, wherein the mobile device comprises a touchscreen; a transaction authentication information unit; one or more sensors coupled to the transaction authentication information unit comprising (1) one or more touchscreen sensors coupled to the touchscreen, (2) an accelerometer, and (3) a gyroscope, the one or more sensors used to obtain and transmit one or more sets of data to the transaction authentication information unit, the one or more sets of data associated with one or more performances of the at least one authentication task by the user; and an anomaly detector coupled to the transaction authentication information unit, wherein the anomaly detector generates an authentication model using the one or more data sets transmitted to the transaction authentication information unit, said generating comprising constructing a set of features for a user profile associated with the one or more performances of the at least one authentication task, and one or more parameters associated with said set of features; the anomaly detector performs training using the one or more data sets transmitted to the transaction authentication information unit, said training comprising learning so as to adjust the one or more parameters associated with the set of features, said learning performed using one or more learning algorithms, and storing the user profile associated with the adjusted one or more parameters in the database; the anomaly detector authenticates the user using the one or more data sets transmitted to the transaction authentication information unit, wherein the anomaly detector analyzes at least one of the one or more data sets corresponding to at least one of the one or more performances of the at least one authentication task using one or more anomaly detection algorithms together with the stored user profile, and based on said analyzing, the anomaly detector decides whether the authentication is successful or unsuccessful.
 2. The system of claim 1, wherein the at least one authentication task comprises a swipe.
 3. The system of claim 1, wherein the accelerometer and gyroscope obtain and transmit a plurality of time series data representing the motion of the mobile device while the at least one authentication task is being performed.
 4. The system of claim 2, wherein the accelerometer and gyroscope obtain and transmit a first plurality of time series data representing the motion of the mobile device while the swipe is being performed; and the one or more touchscreen sensors obtain and transmit a second plurality of time series data representing coordinates of points associated with the swipe.
 5. The system of claim 1, wherein the training comprises setting an initial training window comprising a number of the one or more performances of the at least one authentication task; using some of the one or more data sets corresponding to the number of the one or more performances to perform the learning; and ensuring that the number is sufficiently low so as not to inconvenience the user.
 6. The system of claim 1, wherein the training comprises the anomaly detector setting a rolling window comprising setting a training window comprising a number of the one or more performances of the at least one authentication task, using some of the one or more data sets corresponding to the number of the one or more performances to perform the learning, further wherein if the anomaly detector decides that the authentication is successful, adding a latest of the at least one of the one or more performances of the at least one authentication task used for the successful authentication to the training window, removing an earliest one of the one or more performances of the at least one authentication task from the window, and performing the learning using the data sets corresponding to the one or more performances of the at least one authentication task remaining within the window.
 7. The system of claim 4, further wherein the generating of the authentication model comprises the anomaly detector discretizing the first and second pluralities of time series data transmitted by the accelerator, gyroscope and one or more touchscreen sensors.
 8. The system of claim 7, wherein the one or more parameters comprise at least one of (1) start and end co-ordinates associated with the swipe, (2) direction associated with the swipe, (3) a duration of the swipe, and (4) a length of the swipe.
 9. The system of claim 8, wherein said one or more parameters are represented for each of a plurality of swipes by a corresponding feature vector; the learning further comprising generating an exemplar feature vector for the plurality of swipes by calculating an average using a plurality of said feature vectors, and wherein said authentication is performed based on a distance of another feature vector from the exemplar feature vector; and said another feature vector different from the plurality of feature vectors.
 10. The system of claim 4, wherein each of said first plurality of time series corresponds to an axis in 3-dimensional space, and said stored user profile comprises a maximum and a minimum corresponding to each axis.
 11. The system of claim 10, wherein said maximums and minimums are calculated using a threshold.
 12. The system of claim 4, wherein each of said second plurality of time series corresponds to an axis in 2-dimensional space, and said stored user profile comprises a maximum and a minimum corresponding to each axis.
 13. The system of claim 10, wherein said maximums and minimums are calculated using a threshold.
 14. The system of claim 1, wherein said learning comprises comparing the one or more performances of the at least one authentication task by the user, to one or more attempts by an impostor to imitate the user's one or more performances of the at least one authentication task.
 15. The system of claim 14, wherein said comparing is performed using one or more impostor models, further wherein at least one of said impostor models is based upon empirically-derived observations of attempts by one or more people other than the user to imitate the user's one or more performances of the at least one authentication task.
 16. The system of claim 15, further wherein at least one of said one or more impostor models is based upon an estimate of capabilities of a hypothetical impostor, said estimate obtained via one or more simulations.
 17. The system of claim
 1. further comprising using one or more sets of contextual data to assign a trust level to perform said authentication, the one or more sets of contextual data obtained from at least one of (1) the one or more sensors, (2) a fraud reporting centre connected to the mobile device via a network, and (3) an authentication server connected to the mobile device via a network.
 18. The system of claim 1, further comprising using crowdsourced data to assign the trust level, wherein at least some of the crowdsourced data is obtained by scouring social media sites.
 19. A method for implicit authentication for a mobile device associated with a user, wherein the implicit authentication is behavioural, biometric and task-based, the task-based behavioral biometric implicit authentication comprises at least one authentication task, and the authentication task chosen so as to leverage the user's muscle memory; wherein said mobile device comprises a touchscreen, a transaction authentication information unit, one or more sensors coupled to the transaction authentication information unit, the one or more sensors comprising: (1) one or more touchscreen sensors coupled to said touchscreen, (2) an accelerometer, and (3) a gyroscope, and an anomaly detector coupled to the transaction authentication information unit; said method comprising: obtaining, by the one or more sensors, one or more sets of data associated with one or more performances of the at least one authentication task by the user; transmitting, by the one or more sensors, the obtained one or more sets of data to the transaction authentication information unit; generating, using the anomaly detector, an authentication model using the transmitted one or more data sets, said generating comprising constructing a set of features for a user profile associated with the one or more performances of the at least one authentication task, and one or more parameters associated with said set of features; training the anomaly detector using the one or more data sets transmitted to the transaction authentication information unit, said training comprising learning so as to adjust the one or more parameters associated with the set of features, said learning performed using one or more learning algorithms, storing the user profile associated with the adjusted one or more parameters in the database; and authenticating, by the anomaly detector, the user using the one or more data sets transmitted to the transaction authentication information unit, the authenticating comprising analyzing, by the anomaly detector, at least one of the one or more data sets using one or more anomaly detection algorithms together with the stored user profile, and deciding, by the anomaly detector, whether the authentication is successful or unsuccessful based on said analyzing.
 20. The method of claim 19, wherein the task-based behavioral biometric implicit authentication comprises at least one non-authentication task; and the user does not realize that the at least one non-authentication task is not used for authentication. 